Update good_job 4.1.1 → 4.2.0 (minor) #1221
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ good_job (4.1.1 → 4.2.0) · Repo · Changelog
Release Notes
4.2.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 11 commits:
Release good_job v4.2.0
respect perform_throttle even if perform_limit is provided (#1470)
Update compatibility matrix, remove compatibility code (#1465)
Update cron documentation to remove confusion about multiple processes (#1467)
Run tests with warnings enabled (#1462)
Fix a few method redefinition warnings (#1459)
Do not use advisory lock on heartbeat in production (#1451)
Add appraisal for Rails 7.2; bracket lowest PG version instead of enumerating all (#1460)
Add retry functionality for batches (#1456)
Bump rexml from 3.3.2 to 3.3.3 (#1455)
Remove `smaller_number_is_higher_priority` option from v4 (#1453)
Release Notes
1.11.1 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 9 commits:
Release 1.11.1
Upgrade Ruby test matrix versions
Lower time expectations for labby rubies, gh-104
Add spec for Fugit.parse() and .do_parse, gh-104
Bring in spec helpers from raabro
Add Fugit::Nat.parse() spec input len > 256 gh-104
Add note about nat 256 char limit, gh-104
Peg Fugit::Nat.parse(s) at 256 chars, gh-104
Prepare 1.11.1
Release Notes
5.25.1 (from changelog)
5.25.0 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 24 commits:
prepped for release
- Fix incompatibility caused by minitest-hooks & rails invading minitest internals.
- Revert change from =~ to match? to allow for nil if $TERM undefined.
prepped for release
+ Refactored siginfo handler to reduce runtime costs. Saved ~30%!
normalized all actual/expected var names for assert_equal tests
Accept colon style Hash#inspect in test. (tompng)
- Improve description of test:slow task. (stomar)
- Cleaning up ancient code checking for defined?(Encoding) and the like.
Minor fix to make deprecation tests pass when using rake testW0
oops
+ Fixed some inefficiencies filtering and matching (mostly backtraces).
More foolish consistency...
More foolish consistency... "So many parens!" edition
More foolish consistency...
"A foolish consistency is the hobgoblin of little minds, adored by little statesmen and philosophers and divines"—Emerson
- Disambiguated some shadowed variables in minitest/compress.
Got rid of ANCIENT pre-Integer-merge tests
Got rid of ANCIENT RUBY18 conditioned tests
- Fixed an ironic bug if using string-literals AND Werror.
Finally removed all clean + heredoc for squiggly heredocs in test.
- Added missing rdoc to get back to 100% coverage.
Double quoted some (ancient) string literals.
Fixed 3 tests when using minitest-gcstats.
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands